Replace link to deprecated doc with latest link#22974
Replace link to deprecated doc with latest link#22974cmwilson21 merged 6 commits intogithub:mainfrom
Conversation
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
github-actions
Bot
added
the
triage
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
|
@uhyo Thanks so much for opening a PR! I'll get this triaged for review ⚡ |
cmwilson21
added
content
|
Hi @uhyo, thanks for the PR! ✨ Updating the link looks like a good call--however, I think we'll also need to make a few wording changes around the link. I'll add those now and check the wording with someone on the Codespaces team. |
| - **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization. | ||
| - **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization. | ||
|
|
||
| An organization's administrators specify which repositories should be considered trusted. An admin can [choose to trust](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) none, all, or some of the organization's repositories. A codespace can't have greater permissions to access resources than the person who created it, even if the organization administrator has granted access to all users and all repositories. |
There was a problem hiding this comment.
Should we delete this paragraph, given the feature is deprecated?
There was a problem hiding this comment.
Yes it would make sense to delete this as well based on the deprecation notice.
There was a problem hiding this comment.
Yes, this paragraph should be removed, thanks @isaacmbrown.
isaacmbrown
left a comment
isaacmbrown
left a comment
There was a problem hiding this comment.
Checked on staging -- ready to merge
isaacmbrown
added
ready to merge
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
6 participants
Why:
Hello, I was looking around the docs and found a link to a deprecated explanation about granting Codespaces access to other repositories.
What's being changed (if available, include any code snippets, screenshots, or gifs):
The link is updated to the latest and suggested solution.
Check off the following: